home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Netware Super Library
/
Netware Super Library.iso
/
nov_info
/
fyi8
/
08016.dos
< prev
next >
Wrap
Text File
|
1990-08-01
|
2KB
|
47 lines
Subject: Bug Using NCOPY with the Disk Limitation Feature of v2.1
Date: March 8, 1988
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
GENERAL
INFORMATION: We reported a bug that a customer found. When using the disk
limitation feature of v2.1, a user tries to copy a file that
is larger than the disk space that is allocated for that
user. The file doesn't get copied, but when the user does
a directory listing, they have 0 bytes free. The user still
can copy smaller files that are less than the allocated limit
and they get copied. However, doing another directory
listing still shows 0 bytes free. The only way to get a
correct directory listing is to do a PURGE.
The following is an explanation from our NetWare Utilities
Senior Engineer.
The way NCOPY works for v2.1 is this:
IF (not enough disk space)
THEN print out message of not enough disk space.
Simple enough?
Well, from what you had reported it appears that NCOPY
looked, there wasn't enough space, and it put up the error
message. The reason there wasn't enough space was probably
that the user had deleted a file and had not purged it. The
OS still shows the space for a deleted file as if it is not
deleted until the file is purged. Creating a new file or
deleting an existing file will cause a PURGE. But NCOPY
doesn't cause a PURGE before looking at how much room is
available.
So, we'll modify NCOPY to do it that way. Similar to the
following algorithm:
IF (not enough disk space)
Do a purge.
IF (still not enough disk space)
THEN print out message of not enough disk space.
ELSE copy the file.
ENDIF
We hope this helps. Let us know if we can be of any more
help.